-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Additional tce tests #144650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Additional tce tests #144650
Conversation
|
Some changes occurred in compiler/rustc_codegen_ssa Some changes occurred in compiler/rustc_codegen_gcc |
This comment has been minimized.
This comment has been minimized.
cdfbab1
to
06db3a5
Compare
This comment has been minimized.
This comment has been minimized.
06db3a5
to
0dba4bb
Compare
This comment has been minimized.
This comment has been minimized.
You're gonna need the kind of //@normalize-stderr attributes as other ICE tests have, or just add the test to tests/crashes |
0dba4bb
to
e0738ad
Compare
This comment has been minimized.
This comment has been minimized.
e0738ad
to
e0b4595
Compare
// Indexing taken from | ||
// https://github.com/phi-go/rfcs/blob/guaranteed-tco/text%2F0000-explicit-tail-calls.md#tail-call-elimination | ||
// should probably come back to after some decision on verbiage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by "decision on verbiage"?.. What is this test even testing?
you can make the test pass (hopefully) by just replacing &dyn Fn(usize)
with fn(usize)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Decision on verbiage" was meant to indicate more discussion on examples given in that part of the RFC. From what I could see, nobody had tested that particular example of tail-calling something from a function table, and I was curious as to whether it'd work as desired, as it's kind of an operation. Didn't look too close in that regard though, admittedly.
I can indicate that better with a new comment, thanks for pointing that out.
Test also does pass with the described change. Push coming in a moment. However, it does feel a little silly to include now, so if input indicates I should remove it, I will. I suppose another approach that would include indexing would be something like a "basic examples from RFC" sort of file, or just appending this behavior to another test.
e0b4595
to
1f4a88a
Compare
1f4a88a
to
c9898dc
Compare
@Borgerr I think you broke something in rebase, since you have a commit which is not yours... |
c9898dc
to
caa3cf1
Compare
@rustbot label -S-waiting-on-author +S-waiting-on-review |
@bors r+ |
1fe1bf5
to
27797b1
Compare
This PR changes a file inside |
@rustbot label -S-waiting-on-author +S-waiting-on-review Just moving this to |
@rustbot label +S-waiting-on-author -S-waiting-on-review Wrong issue in file name |
Please give the test a descriptive name, we're trying to move away from test files that only have a number. We can run the try though @bors2 try jobs=dist-i586-gnu-i586-i686-musl
For future reference, |
Additional tce tests try-job: dist-i586-gnu-i586-i686-musl
r? tgross35 |
…or indexing into a function table as described by RFC 3407
27797b1
to
916fb6a
Compare
@rustbot ready Thank you guys again for your patience on this one, this should be it 🙏 |
@bors r=WaffleLapkin,tgross35 |
…ffleLapkin,tgross35 Additional tce tests r? `@oli-obk` Adds known-bug tests for LLVM emissions regarding indirect operands for TCE. Also includes a test, `indexer.rs`, referring to function_table behavior described by the RFC. Depends on rust-lang#144232 Closes rust-lang#144293
r? @oli-obk
Adds known-bug tests for LLVM emissions regarding indirect operands for TCE. Also includes a test,
indexer.rs
, referring to function_table behavior described by the RFC.Depends on #144232
Closes #144293